Skip to content

Replace list with show where possible#3084

Open
renetapopova wants to merge 1 commit into
neo4j:devfrom
renetapopova:dev-change-list-to-show
Open

Replace list with show where possible#3084
renetapopova wants to merge 1 commit into
neo4j:devfrom
renetapopova:dev-change-list-to-show

Conversation

@renetapopova
Copy link
Copy Markdown
Collaborator

No description provided.

Copy link
Copy Markdown
Contributor

@JPryce-Aklundh JPryce-Aklundh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. This PR does, however, raise a question about not using header anchors, since the changes this will effect will likely cause broken links from other manuals.



== Grant privilege to list aliases
== Grant privilege to show aliases
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a broader question I have: does it not make sense to use header anchors in the Ops Manual? Changing these headers may result in broken links from, e.g. the cypher manual and having anchors adds an extra layer of stability.


[[grant-list-auth-rule-privilege]]
== Grant privilege to list auth rules
== Grant privilege to show auth rules
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, for instance, the change in header is risk-free in terms of causing broken links.

====

== Listen address configuration settings
== Showen address configuration settings
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@renetapopova, should we replace 'listen' with 'showen' here?


The procedure for listing queries, `dbms.listQueries()`, is replaced by the command for listing transactions, `SHOW TRANSACTIONS`.
This command returns information about the currently executing query in the transaction.
For more information on the command, see the link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/transaction-clauses#query-listing-transactions[Cypher manual -> `SHOW TRANSACTIONS` command].
Copy link
Copy Markdown
Collaborator

@NataliaIvakina NataliaIvakina May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For more information on the command, see the xref:database-internals/show-and-terminate-transactions.adoc#show-transactions[Database internals -> Show and terminate transactions].

=== Call a procedure without arguments

This example calls the built-in procedure xref:procedures/built-in-procedures.adoc#procedure_db_labels[`db.labels()`], which lists all labels used in the database.
This example calls the built-in procedure xref:procedures/built-in-procedures.adoc#procedure_db_labels[`db.labels()`], which shows all labels used in the database.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I think this procedure just lists all the labels without any further details, so we can use the verb 'lists' here.


[[composite-databases-queries-listing-graphs]]
=== Listing graphs
=== Showing graphs
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here: This is a list of graph names. IMHO, 'Listing' is more accurate.

Copy link
Copy Markdown
Collaborator

@NataliaIvakina NataliaIvakina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall it looks good. I left a few comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants